Reverting breaking change regarding methods with optional parameters #1222
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bachuv
approved these changes
May 23, 2025
sophiatev
deleted the
stevosyan/fix-breaking-methods-with-optional-parameters
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduced breaking changes in that two public methods (ClientEntityHelpers.EmitOperationSignal and OrchestrationEntityContext.EmitRequestMessage) were changed to include optional parameters. Instead, new methods should have been made with these optional parameters and the old methods with the existing method signatures retained. This PR reverts to the old method signatures and introduces the signatures with optional parameters as new methods (which the old methods simply call, passing null for the new parameters).